Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Node E2E: Fix remote log fetching. #37338

Merged

Conversation

Random-Liu
Copy link
Member

@Random-Liu Random-Liu commented Nov 23, 2016

For issue #37333.

This will help debug #37333.

Mark v1.5 because this helps debug an issue #37333, which was originally #35935. /cc @saad-ali

@yujuhong @dchen1107 @jingxu97
/cc @kubernetes/sig-node


This change is Reviewable

@Random-Liu Random-Liu added area/test area/node-e2e release-note-none Denotes a PR that doesn't merit a release note. sig/node Categorizes an issue or PR as relevant to SIG Node. labels Nov 23, 2016
@Random-Liu Random-Liu added this to the v1.5 milestone Nov 23, 2016
@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels Nov 23, 2016
@k8s-github-robot k8s-github-robot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Nov 23, 2016
@@ -299,7 +299,7 @@ func RunRemote(archive string, host string, cleanup bool, junitFilePrefix string
// journald nodes. We should have a more robust way to collect logs.
var (
logName = "system.log"
logPath = filepath.Join(workspace, logName)
logPath = fmt.Sprintf("/tmp/%s-%s", getTimestamp(), logName)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if node is rebooted, the log will still be saved?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

talked offline, it will be saved

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@jingxu97 jingxu97 added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Nov 23, 2016
@k8s-ci-robot
Copy link
Contributor

Jenkins GCI GCE e2e failed for commit e000ff0. Full PR test history.

The magic incantation to run this job again is @k8s-bot gci gce e2e test this. Please help us cut down flakes by linking to an open flake issue when you hit one in your PR.

@jingxu97
Copy link
Contributor

@k8s-bot gci gce e2e test this

@yujuhong
Copy link
Contributor

I see. You did change the path in #35868 :)
LGTM. Maybe add a comment explaining why one should not reuse the workspace as the output directory to prevent regression. OK with adding this comment in a followup PR so that we can start debugging asap.

@k8s-github-robot
Copy link

Automatic merge from submit-queue

@k8s-github-robot k8s-github-robot merged commit 4c7febd into kubernetes:master Nov 23, 2016
@Random-Liu Random-Liu deleted the fix-remote-log-fetching branch November 23, 2016 19:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/node-e2e area/test cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesn't merit a release note. sig/node Categorizes an issue or PR as relevant to SIG Node. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants